home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
kermit.columbia.edu
/
kermit.columbia.edu.tar
/
kermit.columbia.edu
/
newsgroups
/
misc.19970929-19971216
/
000196_news@newsmaster….columbia.edu _Wed Oct 29 09:46:44 1997.msg
< prev
next >
Wrap
Internet Message Format
|
1997-12-15
|
3KB
Return-Path: <news@newsmaster.cc.columbia.edu>
Received: from newsmaster.cc.columbia.edu (newsmaster.cc.columbia.edu [128.59.35.30])
by watsun.cc.columbia.edu (8.8.5/8.8.5) with ESMTP id JAA21970
for <kermit.misc@watsun.cc.columbia.edu>; Wed, 29 Oct 1997 09:46:44 -0500 (EST)
Received: (from news@localhost)
by newsmaster.cc.columbia.edu (8.8.5/8.8.5) id JAA02254
for kermit.misc@watsun; Wed, 29 Oct 1997 09:46:43 -0500 (EST)
Path: news.columbia.edu!watsun.cc.columbia.edu!fdc
From: fdc@watsun.cc.columbia.edu (Frank da Cruz)
Newsgroups: comp.protocols.kermit.misc
Subject: Re: Problem with TRANSMIT / Linux 2.0.27 / Redhat 4.1
Date: 29 Oct 1997 14:46:42 GMT
Organization: Columbia University
Lines: 53
Message-ID: <637i8i$n87$1@apakabar.cc.columbia.edu>
References: <6361ao$b4j@fangorn.fangorn.demon.co.uk>
NNTP-Posting-Host: watsun.cc.columbia.edu
Xref: news.columbia.edu comp.protocols.kermit.misc:7977
In article <6361ao$b4j@fangorn.fangorn.demon.co.uk>,
Adrian Godwin <adrian@fangorn.demon.co.uk> wrote:
:
: I'm having some problems using the TRANSMIT command : the transmission
: stops just short of the end of the file. The amount lost depends on
: various factors (see below), but is generally just a few characters
: short. The behaviour isn't totally repeatable : if I send the same
: file 4 times, it might go OK once.
:
You know, of course, that the TRANSMIT command is a last resort, to be
used when an error-checking-and-correcting protocol is not available, and
that it is very likely to result in corrupted or missing data at the
receiving end, right?
: I'm using :
:
: Kermit 6.0.192 patch 18 (ckermit-6.0.192-7.i386.rpm from columbia)
: Linux 2.0.27 (Redhat 4.1 from Pacific HiTech CDROM)
:
: I suppose I can't be totally sure of the reliability of the serial
: port, PC chipsets and UARTS being what they are.
:
You might have answered your own question right there.
: running Kermit -Y
: ( no difference from symtoms with standard startup script )
:
: set file type { text / bin }
: ( the number of characters lost varies slightly )
:
If you read the manual, you'll see that this also makes a difference in
the number of characters sent.
: enabling local echo
: ( the whole file is echoed to the screen, but not sent to the
: line. There's another effect too : echo only works in binary
: mode, not text )
:
The relevant command is "set transmit echo on".
: Any further suggestions gratefully received.
:
Read the manual? There is a whole chapter on the TRANSMIT command and
how to control it. If you have accounted correctly for the
characteristics of the thing that you are transmitting to and have given
all the appropriate SET TRANSMIT commands, as well as the necessary
communications-related commands -- speed, parity, flow control, etc --
and you still have this problem, then supply all of the details and
settings and we'll take a more detailed look.
Or you might just try cranking the connection down to a lower speed.
- Frank